Location-based payment system and method

ABSTRACT

A virtual payment system including a customer-specific, customer geolocation responsive, limited time duration payment identifier generator operative to generate a customer-specific, customer geolocation responsive, limited time duration payment identifier, a customer-specific limited time duration payment identifier communicator operative to communicate the customer-specific, customer geolocation responsive, limited time duration payment identifier to a customer and a limited time duration payment identifier validator, operative to verify genuineness and timeliness of the customer-specific, customer geolocation responsive, limited time duration payment identifier presented by the customer at a point of sale.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.13/541,089 filed Jul. 3, 2012, which is incorporated herein by referencein its entirety.

FIELD OF THE INVENTION

The present invention relates to payment systems and methodologiesgenerally.

BACKGROUND OF THE INVENTION

Computerized payment systems have been developed to facilitate purchasesof goods and services. Such payment systems are typically deployed atpoints of sale such as retail stores and gas stations.

SUMMARY OF THE INVENTION

The present invention seeks to provide improved payment systems andmethodologies. There is thus provided in accordance with a preferredembodiment of the present invention a virtual payment system including acustomer-specific, customer geolocation responsive, limited timeduration payment identifier generator operative to generate acustomer-specific, customer geolocation responsive, limited timeduration payment identifier, a customer-specific limited time durationpayment identifier communicator operative to communicate thecustomer-specific, customer geolocation responsive, limited timeduration payment identifier to a customer and a limited time durationpayment identifier validator, operative to verify genuineness andtimeliness of the customer-specific, customer geolocation responsive,limited time duration payment identifier presented by the customer at apoint of sale.

Preferably, the customer-specific, customer geolocation responsive,limited time duration payment identifier is also operative as a purchaseidentifier.

In accordance with a preferred embodiment of the present invention thevirtual payment system also includes a point of sale (POS) devicecooperating with the limited time duration payment identifier validator.Additionally, the limited time duration payment identifier validator islocated at the POS device. Alternatively, the limited time durationpayment identifier validator is remotely located from the POS device.

Preferably, the customer-specific, geolocation responsive, limited timeduration payment identifier generator is located at the POS device.Alternatively, the customer geolocation responsive, limited timeduration payment identifier generator is remotely located from the POSdevice.

In accordance with a preferred embodiment of the present invention thelimited time duration payment identifier is valid at a single point ofsale. Alternatively, the limited time duration payment identifier isvalid at multiple points of sale within a geolocation-determined rangeof the customer.

Preferably, the limited time duration payment identifier is valid for ageolocation-determined time which is a function of travel time between alocation of the customer and the point of sale.

There is also provided in accordance with another preferred embodimentof the present invention a virtual payment method including generating acustomer geolocation responsive, limited time duration paymentidentifier, communicating the limited time duration payment identifierto a customer and verifying correctness and timeliness of the limitedtime duration payment identifier presented by the customer at a point ofsale.

Preferably, the customer-specific, customer geolocation responsive,limited time duration payment identifier is also operative as a purchaseidentifier.

In accordance with a preferred embodiment of the present invention theverifying includes verifying at the point of sale. Alternatively, theverifying includes verifying at a location remote from the point ofsale.

Preferably, the generating includes generating at the point of sale.Alternatively, the generating includes generating at a location remotefrom the point of sale.

In accordance with a preferred embodiment of the present invention thelimited time duration payment identifier is valid at a single point ofsale. Alternatively, the limited time duration payment identifier isvalid at multiple points of sale within a geolocation-determined rangeof the customer.

Preferably, the limited time duration payment identifier is valid for ageolocation-determined time which is a function of travel time between alocation of the customer and the point of sale.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood and appreciated more fully fromthe following detailed description, taken in conjunction with thedrawings in which:

FIG. 1 is a simplified functional block diagram of a payment systemconstructed and operative in accordance with a preferred embodiment ofthe present invention;

FIGS. 2A-2G are together a simplified illustration of the structure andoperation of a payment system constructed and operative in accordancewith a preferred embodiment of the present invention; and

FIGS. 3A-3C are together a simplified flowchart illustrating operationof the methodology of a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

Reference is now made to FIG. 1, which is a simplified functional blockdiagram of a payment system constructed and operative in accordance witha preferred embodiment of the present invention. As seen in FIG. 1, thepayment system preferably includes a system server 100, here also termeda “SPEEDCODE” server, which preferably manages the payment system. Thesystem server 100 preferably cooperates with at least one POSconfiguration and management server 102, such as a VERIX® configurationserver commercially available from Verifone, Inc. The at least one POSconfiguration and management server 102 is operative for configuring aplurality of point of sale (POS) devices 104, which are located atbusiness premises, such as convenience stores, and are incorporated intogasoline dispensers, which may be adjunct to the convenience stores. POSdevices 104 may include, for example, payment terminals 106,commercially available from Verifone, Inc., such as a VERIFONE® modelMX® 915, connected to an electronic cash register (ECR) 108. Moregenerally, the POS devices 104 may include one or more of ECRs, paymentterminals, pin pads, and readers, which may be fully or partiallyintegrated and/or interconnected. The payment system of the presentinvention may be used to purchase any suitable goods or services.

The system server 100 preferably interfaces directly or indirectly witha geolocation server 110 which may be cellular-based and/or GPS based.Geolocation server 110 may provide location data for fixed locations113, such as convenience stores 114 and gas stations 116, as well ascurrent location data for a plurality of mobile devices which may be inmotion, such as vehicles and hand-held mobile communicators 118.Geolocation server 110 may also provide navigation instructions leadinga customer from his current location to a selected fixed location 113,such as one of convenience stores 114 and gas stations 116. Geolocationserver 110 may communicate directly with system server 100 or via aSPEEDCODE application resident on a customer mobile communicator 118.

The system server 100 preferably interfaces with one or more financialtransaction processor servers 120, which in turn communicate withfinancial institutions such as banks, credit card companies and PAYPAL®.

The system server 100 and/or the geolocation server 110 preferably alsointerface with one or more merchant location databases 122 which permitmerchant locations to be accessed via merchant identifiers known to POSconfiguration and management server 102.

The system server 100 preferably also interfaces with one or morecustomer location databases 124, which permit current customer locationsto be accessed by the geolocation server 110 via customer identifiersknown to the system server 100. A typical customer identifier may be thecustomer's mobile telephone number or the Temporary Mobile SubscriberIdentity (TMSI).

The system server 100 preferably also interfaces with a customer detailsdatabase 126 which preferably includes, inter alia, a customer vehiclelicense plate number. Database 126 enables a customer vehicle licenseplate number to be accessed by the system server 100 via customeridentifiers known to the system server 100.

The system typically also includes at least one mobile deviceconfiguration server (MDCS) 128, such as Apple App Store or the AndroidPlaystore or a Trusted Secure Manager (TSM) server, commerciallyavailable from Gemalto NV, operative for configuring the plurality ofmobile devices and downloading applications to the mobile communicator118. System server 100 may include this functionality or may communicatewith MDCS server 128.

Typically, POS devices 104 interface with a POS/ECR operating server130, such as a Retail 360 server commercially available from Verifone,Inc., which may also manage, for example, inventory, sales andpromotions. System server 100 may interface with some or all of thevarious POS devices 104, particularly ECRs 108, via POS/ECR operatingserver 130. Alternatively, the system server 100 may interface directlywith the individual POS devices 104. Preferably, system server 100interfaces with payment terminals 106 via POS configuration server 102.Payment terminals 106 are typically in communication with financialtransaction processor servers 120.

It is appreciated that payment terminals 106, ECRs 108, POSconfiguration and management servers 102, POS/ECR operating server 130and system server 100 are typically not under common management control.Merchants and various store operators typically control POS/ECRoperating server 130. Payment terminals 106 and POS configuration andmanagement servers 102 are typically controlled by POS devicemanufacturers and financial institutions. It is also appreciated thatPOS configuration and management servers 102 and POS/ECR operatingservers 130 may be embodied in a single server. It is also appreciatedthat system server 100 may incorporate the functionalities of POSconfiguration and management servers 102 and POS/ECR operating servers130.

Typically, fuel dispensers 132 at gasoline stations 116 interface with afuel dispenser operating server 134. In such a case the system server100 may interface with the various fuel dispensers 132 via the fueldispenser operating server 134. Preferably, fuel dispensers 132 includea payment terminal 106 and a customer interface device 136, whichtypically includes one or more of a keyboard or keypad, a camera, a NFCdevice and a display. Preferably, system server 100 may interface withpayment terminal 106 via POS configuration and management server 102 andwith fuel dispenser 132 and customer interface device 136 via fueldispenser operating server 134.

Reference is now made to FIGS. 2A-2G, which are together a simplifiedillustration of the structure and operation of a payment systemconstructed and operative in accordance with a preferred embodiment ofthe present invention, such as that shown in FIG. 1, and to FIGS. 3A-3C,which are together a simplified flowchart illustrating operation of themethodology of a preferred embodiment of the present invention.

Turning to FIGS. 2A and 3A, it is seen that a customer who wishes to usethe payment system of an embodiment of the present invention, heretermed “SPEEDCODE”, may initially register using his mobile communicator118 via wireless link, such as a cellular telephone link, communicatingwith the system server 100.

Typically, the customer enters the following personal information via atemplate which appears on the display of his mobile communicator 118:name, address, payment account information, vehicle license plate numberand mobile communicator number and transmits this information via thewireless link to system server 100, as indicated at A in FIG. 2A.Normally, within a few minutes, the customer receives, as indicated at Bin FIG. 2A, a confirmation of his SPEEDCODE registration together with aSPEEDCODE ID, typically the customer's mobile telephone number.

As seen particularly in FIG. 3A, customer registration applications arepreferably made available by the system server 100 either directly to acustomer computer or mobile communicator 118, via a suitable website orvia a marketplace such as the Apple App Store or the Android Playstore.Download of this application provides an opportunity for a customer toenter his relevant customer details, preferably including name, mobiletelephone number, address, payment account information, such as creditcard, PAYPAL® or bank account number, vehicle license plate number,vehicle gasoline preference, purchase limits, if any. Upon completion,customer details are communicated to system server 100.

System server 100 verifies validity of the customer details and uponverification enters the customer details into customer details database126 (FIG. 1). The system server 100 preferably sends a registrationconfirmation message to the mobile communicator 118 of the customer.

The system server 100 determines a customer identifier, which may be,for example, the mobile telephone number of the customer or any otheravailable string selected by the customer, and preferably communicatesit to the customer's mobile communicator 118. The customer identifier,here termed also “SPEEDCODE ID,” is preferably confirmed to the customervia the display of the mobile communicator 118. As seen particularly inFIG. 2A, the registration confirmation message and SPEEDCODE ID arepreferably communicated from system server 100 to the mobilecommunicator 118 in a single communication.

Turning to FIGS. 2B and 3B, it is seen that a customer, wishing to usethe virtual payment system of the present invention, preferably selectsthe SPEEDCODE application by touching a suitable icon on his mobilecommunicator 118 and preferably confirms that selection by a furthercustomer action. The application preferably automatically sends theSPEEDCODE ID from the mobile communicator 118 to the system server 100and may also send an account verification code, which may be selected bythe customer and may be provided as part of a wallet application. Thesystem server 100 verifies the SPEEDCODE ID and preferably ascertainsthe current location of the customer, preferably by interaction betweenthe mobile communicator 118 and the geolocation server 110.

Turning now to FIG. 2C, it is seen that the SPEEDCODE applicationpreferably annunciates to the customer, via the customer's mobilecommunicator 118, in an audio and/or visually sensible manner, a menuwhich enables the customer to make purchase selections. For example, thecustomer may indicate that he wishes to purchase gasoline and food andmay specify which food he wishes to purchase. The customer's purchaseselections are communicated to the system server 100.

Turning now to FIG. 2D, it is seen that the system server 100,interfacing with the geolocation server 110 and one or more merchantlocation databases 122, ascertains and then annunciates to the customer,via the customer's mobile communicator 118, the locations andidentifying details, including one or more unambiguous merchantidentifiers, of a plurality of fixed locations 113 which include retailfacilities offering both food and gasoline. These fixed locations 113are typically at various distances and in various directions from thecurrent location of the customer.

The customer may indicate his selection of one or more of the retailfacilities at a selected fixed location 113 of the fixed locations 113annunciated, in which case, driving directions or walking instructionsmay be automatically provided to the customer via the customer's mobilecommunicator 118.

Alternatively, the customer need not communicate a selection of a retailfacility explicitly but may begin driving or walking in a directionwhich indicates that he is heading for one of the indicated retailfacilities. Preferably, once the geolocation server 110 ascertainsunambiguously that the customer is headed for a specific one of theindicated retail facilities, it may request a confirmation from thecustomer, via the customer's mobile communicator, that the customer doeswish to purchase gasoline and/or the selected food at the retailfacility that he appears to be headed for. Alternatively, no suchconfirmation is requested.

Turning now to FIG. 2E, it is seen that in accordance with a preferredembodiment of the present invention, once the customer is within apredetermined propinquity of the selected retail facility, typically1000 feet, the following occurs:

The system server 100 generates and communicates to the customer'smobile communicator 118 a limited duration, single use purchase/payment(LDSU) code. In accordance with one embodiment of the invention, theLDSU code is preferably easily remembered by the customer and thus canbe readily presented by the customer at a point of sale. In such a case,the LDSU code may be annunciated to the customer, preferably via thecustomer's mobile communicator 118. The annunciation may be oral and/orvisual. Alternatively, the LDSU code may be designed to be communicated,such as via NFC, BLUETOOTH and/or WIFI via the customer's mobilecommunicator 118 directly to a POS device 104 and thus need not beeasily remembered by a customer or even annunciated to the customer.

If more than one merchant identifier is present at the selected retailfacility or selected fixed location 113, multiple LDSU codes may beprovided, as seen in FIG. 2E. For example, if gasoline and food are soldby a merchant identified by a single merchant identifier, a single LDSUcode may be employed, however if instead the gasoline sales and the foodsales are controlled by separate entities, having separate merchantidentifiers, as seen in FIG. 2E, multiple LDSU codes may be employed.The LDSU code may be a series of numbers and/or other symbols, includingphrases.

The LDSU code is preferably valid for a short period of time, normallydenominated in minutes, sufficient to allow the customer to reach theretail facility and complete the fuel dispensing and/or purchaseactivity. After the limited duration, the code expires and can no longerbe used for a transaction. Once the code is used, it expires. Theduration may be a function of the sensed propinquity, in terms of timeor distance of the customer from the retail facility at the time of LDSUcode generation.

The LDSU code may be valid at a single retail facility or alternativelyat multiple retail facilities.

It is appreciated that system server 100 may communicate the LDSU codeto the customer's mobile communicator 118 immediately after LDSUgeneration.

Turning now to FIG. 3C, it is seen that the system server 100 may send amessage to the selected retail facility, preferably via the POSoperating server 130, and alternatively via a merchant server, ordirectly via a POS device, placing an order for the selected food, toenable it to be prepared for delivery prior to arrival of the customerat the retail facility. This message preferably indicates the estimatedarrival time of the customer at the retail facility.

As seen in FIG. 2F, arrival of the customer vehicle at the retailfacility may be sensed via GPS or by reading the customer's vehiclelicense plate by a reader interfacing with the a fuel dispenseroperating server 134 and with system server 100. In the latter case, thevehicle's license plate may be recognized as corresponding to aregistered SPEEDCODE customer who has indicated his wish to purchasegasoline within the limited duration established by the LDSU code and aspecific fuel dispenser adjacent which the vehicle is located mayprovide a customer specific message to the customer, inviting thecustomer to display or otherwise enter the LDSU code. A message may becommunicated from system server 100 to the POS/ECR operating server 130notifying the arrival of the customer to the adjacent gasoline station.

In either case, the customer is invited to display or otherwise enterthe LDSU code. This may be done, for example, using a customer interfacedevice 136, such as a keyboard or keypad, camera or NFC device, as byplacing the display of the customer's mobile communicator 118 in frontof a camera or by using NFC communication.

If no licensed plate recognition is provided, the customer may selectpayment via SPEEDCODE and then proceed to enter his LDSU code.

Preferably, while the customer is present at the selected the retailfacility, the LDSU code is either displayed or readily displayable orotherwise annunciatable by the customer's mobile communicator 118.

Upon entry of the LDSU code in any of the foregoing ways, followingreceived LDSU validity verification by system server 100 or by one of aPOS device, a merchant server and a POS operating server 130 at theretail facility, a fuel dispenser 132 is enabled to dispense the type offuel that was indicated by the customer upon registration and a POSdevice 104. The fuel dispenser 132 is automatically operated tointerface with the system server 100 to obtain the necessary paymentparticulars to enable completion of the payment via payment terminal 106communicating to financial transaction processor servers 120.Alternatively, completion of the payment transaction may be effected bythe system server 100, a financial transaction processor server 120 andone or more of a merchant server and POS operating server 130 withoutinvolving a payment terminal 106 at the fuel dispenser.

As seen in FIG. 2G, customer's food order is delivered. LDSU ispresented to a payment device 106. Non-gasoline purchase transactionsmay be carried out automatically in a similar manner by the systemserver 100 either via a POS device 104 located at the store or bypayment device 106 or independently thereof by interactions between thesystem server 100, a financial transaction processor server 120 and oneor more of a merchant server and POS operating server 130.

In an alternative system configuration, the geolocation server isobviated. The customer may select a geographical area, for example NewYork City, from an application menu, and may or may not indicate goodsor services to be purchased, for example, SELL OIL Gasoline. An LDSUcode valid for a predetermined limited time duration, for example, 10minutes, is generated by system server 100 and communicated to thecustomer's mobile communicator 118 as well as to all SELL OIL retailfacilities within New York City. The customer may purchase gasoline orpossible other products or services from any SELL OIL retail facilitiesin New York City during the validity of the LDSU code in the mannerdescribed hereinabove.

It will be appreciated by persons skilled in the art that the presentinvention is not limited by what has been particularly shown anddescribed hereinabove. Rather the scope of the present inventionincludes both combinations and subcombinations of the various featuresdescribed hereinabove as well as modifications thereof which are not inthe prior art.

The invention claimed is:
 1. A virtual payment method comprising:generating a customer-specific, merchant specific, customer geolocationresponsive, limited time duration payment identifier, wherein generatingis conducted, automatically, by a customer-specific, merchant specific,customer geolocation responsive, limited time duration paymentidentifier generator, comprising at least one computer processor, and isgenerated in response to a customer order for at least one specificproduct; communicating said customer-specific, merchant specific,customer geolocation responsive, limited time duration paymentidentifier to a customer; and verifying correctness and timeliness ofsaid customer-specific, merchant specific, customer geolocationresponsive, limited time duration payment identifier when presented bysaid customer to a point of sale device at a merchant location, whereinthe correctness and timeliness is verified by a limited time durationtransaction identifier validator in communication with the point of saledevice; wherein the generating of said customer-specific, merchantlocation-specific, customer geolocation responsive, limited timeduration transaction identifier occurs remotely from said point of saledevice.
 2. The virtual payment method according to claim 1 and whereinsaid customer-specific, merchant specific, customer-specific, customergeolocation responsive, limited time duration payment identifier isoperative as a purchase identifier.
 3. The virtual payment methodaccording to claim 1 and wherein the limited time duration transactionidentifier validator is co-located with said point of sale device. 4.The virtual payment method according to claim 1 and wherein the limitedtime duration transaction identifier validator is located at a locationremote from said point of sale device.
 5. The virtual payment methodaccording to claim 1 and wherein said customer-specific, merchantspecific, customer-specific, customer geolocation responsive, limitedtime duration payment identifier is valid at a single point of saledevice.
 6. The virtual payment method according to claim 1 and whereinsaid customer-specific, merchant specific, customer-specific, customergeolocation responsive, limited time duration payment identifier isvalid at multiple point of sale devices within a geolocation-determinedrange of said customer.
 7. The virtual payment card method according toclaim 1 and wherein said limited time duration payment identifier isvalid for a geolocation-determined time which is a function of traveltime between a location of said customer and said point of sale deviceat the merchant location.